docs(openapi): Align 404 to use generic error and specific example#2422
docs(openapi): Align 404 to use generic error and specific example#2422
Conversation
Add missing, but possible errors to the ErrorResponse.yaml
|
Preview for this PR was built for commit |
|
A PR to update the Python client models has been created: apify/apify-client-python#719 This was automatically triggered by OpenAPI specification changes in this PR. |
vdusek
left a comment
There was a problem hiding this comment.
please see what it generated in apify/apify-client-python#719 - ErrorType, Type1
…es in generated code
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
ae3efa9 to
58d9566
Compare
|
Preview for this PR was built for commit |
|
The Python client model PR has been updated with the latest OpenAPI spec changes: apify/apify-client-python#719 |
This PR updates the auto-generated Pydantic models based on OpenAPI specification changes in [apify-docs PR #2422](apify/apify-docs#2422). --------- Co-authored-by: apify-service-account <apify-service-account@users.noreply.github.com>
ErrorResponse.yamlMotivation:
last runendpoints always havingactor/run not founderrors even when referring to the default dataset, while getting the dataset directly through id will never return such 404 variant )Follow up for: #2398
Partially implements: #2286